-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DO NOT MERGE] Use only CUDA devices with a supported architecture #299
base: CMSSW_11_1_X_Patatrack
Are you sure you want to change the base?
[DO NOT MERGE] Use only CUDA devices with a supported architecture #299
Conversation
Second attempt at #286, mostly to check if we can find a working set of CUDA build rules for this use case. |
The present CUDA rules do not allow to have .cu files both in a shared library and in a plugin. |
Just to note (in case it was not intentional) that now there are implementations of |
Sorry about that, I'll clean it up. |
For each available CUDA device, check if its architecture is supported running a simple kernel. This allows to restrict using only the supported devices - at configuration time, in the SwitchProducerCUDA, via the cudaIsEnabled test; - at run time, in the CUDAService and its clients; - when running tests, via exitSansCUDADevices. Includes Matti's fix for the sizes of stream and event caches (cms-sw#289).
2be0bc1
to
8deb1d9
Compare
The logic here
cmssw/HeterogeneousCore/CUDACore/interface/CUDAESProduct.h Lines 32 to 35 in 586c0c0
needs to be updated as well. |
For each available CUDA device, check if its architecture is supported running a simple kernel.
This allows to restrict using only the supported devices
Includes Matti's fix for the sizes of stream and event caches (#289).